Exporting based on Baseline event

Does anyone know if this is possible? I am trying to force an export to a specified location based on the event of baseline completion.
JGamble - Mon May 03 12:41:02 EDT 2010

Re: Exporting based on Baseline event
Mathias Mamsch - Mon May 03 16:39:00 EDT 2010

You cannot "hook" the baseline creation itself, but you can maybe leverage the fact the module is reopened when it is baselined, so you could probably do a module open trigger and look in the history for a baseline creation.

The question would be: If you have a baseline anyway (which nobody can easily change), why bother to export it *right away*? If you export it later you probably will not get different data. You could do a periodical script which exports the baselines of a bunch of modules every night. Or you could provide the user with a custom baseline script that will run the export after the baseline automatically.

Forcing exports is probably not a good idea in most cases - better you just give the user help to remember doing an export if he needs to do it.

Hope this helps, regards, Mathias


Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Re: Exporting based on Baseline event
JGamble - Wed May 05 09:34:17 EDT 2010

Mathias Mamsch - Mon May 03 16:39:00 EDT 2010
You cannot "hook" the baseline creation itself, but you can maybe leverage the fact the module is reopened when it is baselined, so you could probably do a module open trigger and look in the history for a baseline creation.

The question would be: If you have a baseline anyway (which nobody can easily change), why bother to export it *right away*? If you export it later you probably will not get different data. You could do a periodical script which exports the baselines of a bunch of modules every night. Or you could provide the user with a custom baseline script that will run the export after the baseline automatically.

Forcing exports is probably not a good idea in most cases - better you just give the user help to remember doing an export if he needs to do it.

Hope this helps, regards, Mathias


Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Thanks Mathias,

The problem that I am facing is automation between DOORS and SA. I have tried many ways to improve the process that binds these two useful tools together, but 'the man' still wants more automation. So in my best effort I came up with a plan to export the requirements when ever they change i.e. a new baseline (We baseline after large change events).
My overall goal in steps in DOORS is as follows:
1. Baseline
2. Run Baseline Compare (Cutting the view down to only requirements that changed)
3. Export results to CSV

Once the changes are in the CSV, I have a script from within SA that will go to the CSV and check to see if the file has changed, if so import the requirements if not 'do nothing'.

My biggest problem is I have very little background in C/C++ but I can code in VB farely well. I may go at this a different way, but I am certain that I can get this code to work with a few cups of coffee.